-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug fix]remove paddle.nn.Sequential to fix dygraph to static error #48477
[bug fix]remove paddle.nn.Sequential to fix dygraph to static error #48477
Conversation
你的PR提交成功,感谢你对开源项目的贡献! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
之前因为循环依赖的问题,将Sequential复制一份实现放到paddle.nn下,保留原有Sequential实现 等到动转静完成迁出fluid以后,可将Sequential 从fluid下完全迁移到paddle.nn |
The description should be clear why remove |
added description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for docs
PR types
Bug fixes
PR changes
APIs
Describe
In the previous work of cleaning
Sequential
under fluid, due to the problem of circular dependency, I copied a copy ofSequential
and put it under paddle.nn, and kept the originalSequential
under fluid.In dygraph to static,
paddle.fluid.dygraph.dygraph_to_static.convert_call_func.py
importspaddle.fluid.dygraph.container.Sequential
under fluid on line 27, and performs type judgment on lines 48 and 131, which will lead to an obscure problem. Usepaddle.nn.Sequential
models will not be able to perform dygraph and static conversions correctly.So we remove the Sequential under paddle.nn, and will migrate it back after the dygraph to static migration is completed.